Skip to content

Conversation

@stasm
Copy link
Contributor

@stasm stasm commented Dec 3, 2018

Fix #315 (to an extent). I didn't want to add spans manually, so I still kept getSimpleExpression as a separate method. (Simple as opposed to member expression; I'm open to other naming.) I think that once we implement projectfluent/fluent#221, we'll be able to simplify this further.

I'll clean up the commit messages before landing.

@stasm stasm requested a review from Pike December 3, 2018 12:16
@stasm stasm force-pushed the getInlineExpression branch from add76c2 to bcdf6ef Compare December 3, 2018 12:17
@stasm stasm force-pushed the getInlineExpression branch from bcdf6ef to a4dcbea Compare December 3, 2018 12:20
Copy link
Contributor

@Pike Pike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the outcome here, r=me.

We should do something about the error codes of the past, but in a different issue. File #319 for that.


if (ps.currentChar === "-") {

if (ps.peek() !== ">") {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be more strict in checking the -> syntax here. I'll fix this as part of a future refactor to reduce the use of peek() and next().

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I filed #320 for this.

@stasm stasm merged commit 1cc091f into projectfluent:zeroeight Dec 4, 2018
@stasm stasm deleted the getInlineExpression branch December 4, 2018 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants